|
Disciplined agile delivery (DAD) is a process decision framework that enables simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including Scrum, agile modeling, lean software development, and others. The primary reference for disciplined agile delivery is the book of same name, written by Scott Ambler and Mark Lines. In particular, DAD has been identified as a means of moving beyond Scrum. According to Cutter Senior Consultant Bhuvan Unhelkar, "The DAD framework provides a carefully constructed mechanism that not only streamlines IT work, but more importantly, enables scaling.".〔Disciplined Agile Delivery in the Enterprise (Cutter IT Journal, Special Issue, June 2013)〕 Paul Gorans and Philippe Kruchten call for more discipline in implementation of agile approaches and indicate that DAD, as an example framework, is "a hybrid agile approach to enterprise IT solution delivery that provides a solid foundation from which to scale." == History == "DAD is a second-generation framework that strives to provide a coherent, end-to-end strategy for how agile solution delivery works in practice. DAD is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value lifecycle, is goal-driven, is scalable, and is enterprise aware."〔Disciplined Agile Delivery: the foundation for scaling agile (Crosstalk journal, November / December 2013)〕 Scott Ambler developed the disciplined agile development process during his time as chief methodologist for IT at IBM Rational (Summer 2006 to Summer 2012). It was developed to provide a more cohesive approach to agile software development; one that fills in the process gaps that are (purposely) ignored by Scrum, and one that is capable of enterprise-level scale. According to Ambler, "Many agile methodologies — including Scrum, XP, AM, Agile Data, Kanban, and more — focus on a subset of the activities required to deliver a solution from project initiation to delivery. Before DAD was developed, you needed to cobble together your own agile methodology to get the job done."〔Disciplined Agile Delivery Meets CMMI (Cutter IT Journal, November 2013)〕 The DAD framework was developed as a result of observing common patterns where agility was applied at scale successfully. It reflects the experiences of IBM employees working in the field with various customer organizations, applying agile at scale internally, and from working with various business partners.〔(【引用サイトリンク】url=http://m.crosstalkonline.org/issues/10/82/ )〕 "The DAD process framework recognizes not only the importance of networks of cross-functional teams, it also explicitly offers support for scaling key practices across complex working environments using techniques that link software development efforts into robust software delivery contexts". 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Disciplined agile delivery」の詳細全文を読む スポンサード リンク
|